home *** CD-ROM | disk | FTP | other *** search
- Path: news.cs.tut.fi!usenet
- From: p150650@korppi.cs.tut.fi (Tero Pulkkinen)
- Newsgroups: comp.lang.c++
- Subject: Re: g++ generating huge executables for simple programs
- Date: 15 Jan 1996 15:20:27 +0200
- Organization: Tampere University of Technology, Finland
- Sender: p150650@korppi.cs.tut.fi
- Distribution: inet
- Message-ID: <xdu68edegro.fsf@korppi.cs.tut.fi>
- References: <4d3vuk$7l9@cloner2.ix.netcom.com>
- NNTP-Posting-Host: korppi.cs.tut.fi
- NNTP-Posting-User: p150650
- In-reply-to: ruiner@ix.netcom.com's message of Thu, 11 Jan 1996 21:35:46 GMT
- X-Newsreader: Gnus v5.0.13
-
- G++ is generating HUGE executable files for source code that is only
- five or six lines long on the CS computers at my school
- (pegasus.cs.tulane.edu). A program called "strip" seems to reduce the
- problem to about 180K, but thats still a gross waste of space. Are the
- CS administrators correct in saying nothing more can be done to
- alleviate the problem? I believe they are running a recent ver of IBM
- AIX, if thats any help. I cannot write serious programs if they turn
- out so wastefully big, so please help. email and post please.
-
- Check out which libraries does it include to your program, and when
- necessary, replace the libraries with your own versions of the
- library. Also there's usually startupcode which parses argc and argv
- and initializes stack included. Those are the only things you can
- take from the file size. Tho, removing either of those will disable
- some of the features standard C offers, like displaying text or
- opening files. (These are for any compiler, and i'm not saying this
- is possible or feasible in g++)
- But trying to figure out what's in those 180kb will help for sure.
-
-
- -- Tero Pulkkinen -- terop@kotka.cs.tut.fi --
-